Task: Release Build
Product or Component Build to be released and published to external and internal users.
Disciplines: Build Management
Purpose

Packages release for distribution to the development team’s customer.

Relationships
RolesPrimary Performer: Additional Performers:
InputsMandatory:
    		Optional:
      Outputs
        Main Description

        The Release Build is the "formal" releasing process for the application.

        Some components may require delivery and distribution of their source code in order to build other components; while other components may require delivery and distribution of only binaries, or binaries and interface definitions (e.g., header files in C/C++).

        Steps
        Define the build completness

        In order to improve the quality and reliability of the final release build, the build completness can be a clean full build.

        Identify Release Type

        It is suggested that the release type (beta, bugfix, cadidate...) should be reflected in the relese Label version. E.g. PRODUCT-REL-01.00B or PRODUCT-REL-01.00C.

        This same release label should be a parameter to Release Build script, to be included in some manifest file in order to be possible to later identify given a certain package what version is it.

        Launch Build
        Launch Build using the command line with the resolved compile time variabilities if applicable. (Is Preferrable the build command to be the same as the Continuous integration one)
        Apply Label on Repository build Configuration
        Apply Label on Repository build Configuration
        Key Considerations
        Packaging the release for distribuition should be an automated step in the build script, to avoid manual packaging failures.